Determining Response Signature Commonalities

ABSTRACT

An analyzer can obtain data regarding signal characteristics in each of multiple communication channels within an access network. The analyzer can use that data to create signatures corresponding to each of the multiple channels. Based on similarities between signatures, the analyzer may then identify clusters of signatures associated with devices that share channels or portions of channels.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority to Provisional U.S. Patent Application Ser. No. 61/301,835, filed Feb. 5, 2010, and titled “Modem Signal Usage and Fault Isolation,” which application in its entirety is incorporated by reference herein.

BACKGROUND

Many communication networks include multiple individual access devices communicating with a hub device. Anomalies in a path between an access device and a hub can impair signal transmission. Although various methods for compensating for such anomalies are known, there remains a need for improved analysis techniques.

SUMMARY

This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the disclosure.

In at least some embodiments, an analyzer can obtain data regarding signal characteristics in each of multiple communication channels within an access network. Each channel may be associated with an individual access device and can represent a physical path from that individual access device to a termination system or other type of hub. The analyzer can use the obtained data to create signatures corresponding to each of the multiple channels. Based on similarities between signatures, the analyzer may then identify clusters of signatures associated with devices that share channels or portions of channels. These signature clusters can be used to diagnose and locate network problems, to identify unauthorized and/or unprovisioned devices, and/or for other purposes. Other embodiments are discussed below.

BRIEF DESCRIPTION OF THE DRAWINGS

FIGS. 1A-1M are graphs illustrating multiple frequency response signatures for communication paths in an access network.

FIG. 2 is a block diagram showing elements in an access network in which some embodiments may be practiced.

FIG. 3 is a block diagram showing an exemplary analyzer according to some embodiments.

FIG. 4 is a flow chart showing operations performed by an analyzer according to at least some embodiments.

FIGS. 5A-5E shows portions of a database used by an analyzer according to some embodiments.

FIG. 6 is a flow chart showing additional details of operations in the flow chart of FIG. 4.

FIGS. 7A-7E graphically illustrate operations that may be performed in connection with the flows shown in FIGS. 6 and 8.

FIG. 8 is a flow chart showing additional details of operations in connection with the flow chart of FIG. 6.

FIGS. 9A-9C show exemplary analyzer output displays according to some embodiments.

FIG. 10 is a flow chart showing additional details of operations in the flow chart of FIG. 4 according to at least some embodiments.

FIGS. 11A-11C are examples of frequency response signatures in a network.

FIG. 12 is a flow chart showing additional details of operations in the flow chart of FIG. 4 according to at least some embodiments.

DETAILED DESCRIPTION

FIGS. 1A-1M illustrate channel signatures and signature clusters for communications between access devices and a hub in an access network. In the example of FIGS. 1A-1M, the access devices are modems (e.g., cable modems) and the hub is a termination system (e.g., a cable modem termination system (CMTS)) in an access network, such as a hybrid fiber coaxial (HFC) access network. Although some embodiments are described in the context of communications (e.g., upstream communications) between modems and a termination system in an access network, other embodiments include different types of access devices (e.g., fiber optic modems, wireless transceivers, gateways, set top terminals, digital video recorders), different types of hubs (e.g., other types of termination systems, optical line terminals, wireless base stations, satellites), and/or different types of networks. Such networks may use any of numerous communication protocols. Such networks may also utilize various different types of physical communication media (e.g., twisted pair conductors, wireless RF communications, fiber optical link). Examples of such other networks in other embodiments include fiber optic, satellite and other wireless communication networks, digital subscriber line (DSL) networks, etc.

FIG. 1A shows multiple waveforms superimposed on one another. Each waveform in FIG. 1A is associated with a different one of multiple access devices communicating with a hub. Specifically, each waveform is a graphical representation of an amplitude versus frequency response (or “amplitude/frequency response”) signature for upstream communications from the associated access device to the hub. Each signature therefore also corresponds to a specific communication path between the associated access device and the hub. The vertical axis in the graph of FIG. 1A represents signal power in decibels (dB). In the example of FIGS. 1A-1M, that carrier is a 6.4 MHz channel centered at 23.2 MHz. The horizontal axis of FIG. 1A represents negative and positive deviations from that center frequency, with the center frequency shown as “0” on the horizontal axis. As explained in more detail below, each signature represented in FIG. 1A is derived from a fast Fourier transform (FFT) of the pre-equalization coefficients for the associated access device. The horizontal axis of FIG. 1A is divided into units of frequency. In particular, each unit on the horizontal axis represents 0.1 (or 10%) of the spectrum being analyzed. In the case of the 6.4 MHz channel of FIGS. 1A-1M, 5.12 MHz of channel alpha is used. The remainder (1.28 MHz) is disregarded due to roll-off effect near the channel edges.

As seen in FIG. 1A, an amplitude/frequency response signature can include multiple wave-like ripples of varying size and having different positions relative to the center frequency. Ripples in a response signature associated with a particular access device often result from some type of damage, imperfection or other anomaly in the physical communication path between that associated access device and the termination system or other hub. Examples of such imperfections can include loose or missing connectors, corroded couplers, corroded connections, impedance mismatches from incorrectly selected components, internal modem filters, a damaged cable section, and idiosyncratic frequency responses of filters or other components. The number of ripples in a signature, as well as the height, width and position of each ripple, can be affected by the number, type(s), severity and location(s) of anomalies in the communication path corresponding to that signature.

Because a response signature is affected by anomalies in the corresponding communication path, a response signature can often be used to distinguish one or more paths in a network from other paths in that same network. In some cases, for example, each access device in a set of access devices may have a unique communication path to a hub. However, each of those paths may include a portion used by a single one of those devices and portions shared with other devices. As one illustration, each of multiple access devices in a neighborhood may have a communication path to a hub that includes a first portion used only by that access device (e.g., a tap line to an individual residence), a second portion shared with a small number of other devices (e.g., a feeder line serving devices on a particular street), a third portion serving a larger set of devices (e.g., a trunk line serving devices on several streets), etc. An anomaly in one of those shared network portions will often cause the access devices using that shared portion to have associated response signatures that are similar to one another. However, those response signatures may be distinguishable from signatures associated with devices not using the shared network portion. By finding similarities between response signatures and the extent to which those similarities apply to other devices, the likely location of a plant anomaly can be determined. For example, similar signatures associated with access devices in a neighborhood, but not associated with devices in adjacent neighborhoods, suggest an anomaly in a tap or other plant element serving only that neighborhood.

Similarities among different collections of response signatures are illustrated in FIGS. 1B-1E. For example, a portion of the signatures from FIG. 1A having a first general shape are separately shown as cluster 1 in FIG. 1B. Each of the cluster 1 signatures has the same number of ripples. Moreover, the sizes and positions of ripples in each of the cluster 1 signatures are very similar to the sizes and positions of ripples in the other cluster 1 signatures. Another subset of the signatures from FIG. 1A having a second general shape is shown as cluster 2 in FIG. 1C, with each of the cluster 2 signatures being very similar in number, size and position of ripples. Yet another cluster of the signatures from FIG. 1A having a third general shape is shown in FIG. 1C as cluster 3. Based on the similarity of the signatures within each of clusters 1-3, the access devices associated with signatures in a particular cluster likely share a significant portion of a communication path. Using knowledge of the physical plant in the network and/or the location of one or more access devices associated with a particular cluster, the likely location of other access devices associated with that cluster and/or of plant anomalies can be accurately estimated.

In some cases, a large portion of signatures in an access network may have relatively few ripples. For example, a large subset of signatures having relatively small ripples are concentrated as a horizontal “rope” of signatures at the center of FIG. 1A. These signatures are shown separately as cluster 4 in FIG. 1E. As explained in further detail below, however, analysis parameters can be adjusted to further distinguish between signatures and/or sub-clusters of signatures within cluster 4.

The same data used to generate amplitude/frequency response signatures for individual access devices can be used to generate other types of response signatures. Those other signature types can also be used to distinguish among communication paths in a network. For example, an FFT of the pre-equalization coefficients of the cable modems associated with FIG. 1A can also be used to create a group delay vs. frequency response signature for each of those cable modems. “Group delay” (GD) can be defined as the negative derivative of phase with respect to frequency, expressed mathematically as GD=−(dφ/dω) and having units of time such as nanoseconds, and represents a measure of the extent to which signals at some frequencies travel faster than signals at other frequencies. As another example, an FFT of those same pre-equalization coefficients can further be used to create a phase delay vs. frequency response signature for each of those cable modems. “Phase delay” can be defined as the time delay (e.g., in nanoseconds) experienced by each sinusoidal component of an input signal. As with an amplitude/frequency response signature, the numbers, sizes and positions of ripples in a group delay/frequency response signature or in a phase delay/frequency response signature can be affected by the number, type(s), severity and location(s) of anomalies in a communication path. However, some anomalies may have different effects on different types of frequency response signatures.

FIGS. 1F-1I show four clusters of group delay/frequency response signatures generated using the same data used to create the amplitude/frequency response signatures of FIGS. 1A-1E. All of the signatures in cluster 5 (FIG. 1F) generally have the same number of ripples, with those ripples having similar sizes and positions in each cluster 5 signature. The same is true with regard to the signatures in clusters 6 (FIG. 1G) and 7 (FIG. 1H), with cluster 8 including signatures in a concentrated rope similar to that of FIG. 1E. Although each of the group delay/frequency response signatures in clusters 5-8 is associated with a cable modem (and corresponds to a communication path) for which an amplitude/frequency response signature is included in FIG. 1A, the associations of cable modems in clusters 1-4 is not necessarily the same as the associations of cable modems in clusters 5-8. For example, a cable modem might be associated with an amplitude/frequency response signature in cluster 4 but be associated with a group delay/frequency response signature in one of clusters 5, 6 or 7.

FIGS. 1J-1M show four clusters of phase delay/frequency response signatures also generated using the same data used to create the amplitude/frequency response signatures of FIGS. 1A-1E. Within each of clusters 9 (FIG. 1J), 10 (FIG. 1K) and 11 (FIG. 1L), each of the cluster signatures generally has the same number of ripples and has ripples of similar sizes and positions. Cluster 12 includes signatures in a concentrated rope similar to that of FIG. 1E. Although each of the phase delay/frequency response signatures in clusters 9-12 is associated with a cable modem (and corresponds to a communication path) for which an amplitude/frequency response signature is included in FIG. 1A, and for which a group delay/frequency response signature may be included in one of FIGS. 1F-1I, the association of cable modems in clusters 9-12 is not necessarily the same as the associations of cable modems in clusters 1-4 or in clusters 5-8.

FIG. 2 is a block diagram showing elements in an exemplary access network 50 according to some embodiments. Each of multiple access devices (AD) 51-1 through 51-N communicates with a hub 52 across a particular path through network 50. Each of devices 51-1 through 51-N may share a large part of its communication path to hub 52 with a relatively small portion of the other devices 51-1 through 51-N (e.g., access devices on the same street, on the same building floor, or otherwise in the same relatively small geospatial region). Each of devices 51-1 through 51-N may share a slightly smaller part of its communication path to hub 52 with a slightly larger portion of the other devices 51-1 through 51-N (e.g., access devices in the same neighborhood, in the same building, or otherwise in the same slightly larger geospatial region). This pattern may continue for larger sets of access devices.

In some embodiments, and as previously indicated in connection with FIGS. 1A-1M, hub 52 may be a CMTS or other type of termination system, network 50 may be an HFC access network, and access devices 51-1 through 51-N may be cable modems or other devices (e.g., a set top terminal) communicating via the HFC access network. In other embodiments, network 50 may be a digital subscriber line (DSL) network, hub 52 may be a DSL access module (DSLAM), and access devices 51-1 through 51-N may be DSL modems or other devices communicating via the DSL network. In still other embodiments, network 50 may be a satellite of other wireless network employing adaptive equalization, access devices 51-1 through 51-N may be transceivers through which users can access the wireless network, and hub 52 may be a base station or other wireless network hub. In yet other embodiments network 50 may be a Fiber to the Home (FTTH) or Fiber to the Premises (FTTP) passive optical network (PON).

Hub 52 may communicate over one or more links 54 (e.g., a Gigabit Ethernet link) with the Internet, a private IP (internet protocol) data network, and/or other network so as to allow communications between devices 51-1 through 51-N (via hub 52) and one or more external networks. In the examples of FIG. 2 and subsequent figures, “N” represents an arbitrary number. Network 50 may include hundreds, thousands or more access devices. Hub 52 may also utilize links 54 for communication with billing servers, network management servers, and/or other network elements. One such network element is analyzer 53. Analyzer 53 retrieves data from hub 53 regarding the signal characteristics in communication paths between devices 51-1 through 51-N and hub 52. In some embodiments, this data includes pre-equalizer tap coefficients from devices 51-1 through 51-N. Analyzer 53 then processes the retrieved data to create signatures associated with devices 51-1 through 51-N, to identify devices that share communication paths or portions of paths, to diagnose and locate network problems, to identify unauthorized and/or unprovisioned devices, and/or perform other operations described herein. Although FIG. 2 shows analyzer 53 communicating with hub 52 over link 54, analyzer 53 could alternately be connected to (or a part of) hub 52.

FIG. 3 is a block diagram of an exemplary analyzer 53 according to some embodiments. In at least some embodiments, analyzer 53 can be implemented as (or as part of) a general purpose computer. Such a general purpose computer could be dedicated to performing analyzer 53 operations described herein, or could also perform other operations. Analyzer 53 communicates with hub 52 and/or other network elements over one or more network interfaces (i/f) 83. Interface 83 could be, e.g., a Gigabit Ethernet card. Analyzer 53 further includes memory 82 for storing instructions and data and a processor 81 for executing instructions and controlling operations of analyzer 53. Although a single block is shown for memory 82 and a single block shown for processor 81, memory and computational operations of analyzer 53 could respectively be distributed across multiple memory devices and multiple processors located within analyzer 53 or spread across multiple platforms (e.g., multiple general purpose computers). Memory 82 may include volatile and non-volatile memory and can include any of various types of storage technology, including but not limited to read only memory (ROM) modules, random access memory (RAM) modules, magnetic tape, magnetic discs (e.g., a fixed hard disk drive or a removable floppy disk), optical disk (e.g., a CD-ROM disc, a CD-RW disc, a DVD disc), flash memory, and EEPROM memory. Processor 81 may be implemented with any of numerous types of devices, including but not limited to general purpose microprocessors, application specific integrated circuits, field programmable gate arrays, and combinations thereof. In at least some embodiments, processor 81 carries out operations of analyzer 53 described herein according to machine readable instructions stored in memory 82 and/or stored as hardwired logic gates within processor 81. Processor 81 communicates with and controls memory 82 and interface 83 over one or more buses 84.

Analyzer 53 can output data to a user on a display 86 using video interface 85. Although not shown, analyzer 53 may also receive user input via a keyboard, mouse or other input device. In some embodiments, analyzer 53 may communicate with other computers over network interface 83. For example, a user having a laptop computer or other computing device could establish a communication session with analyzer 53 over one or more network links. The user could provide instructions, submit queries or otherwise interact with analyzer 53 by sending communications over the network links. Analyzer 53 could then provide data outputs to the user's computer over those same links, which data could then be output on a display of the user's computer.

FIG. 4 is a flow chart showing operations performed by analyzer 53 according to at least some embodiments. Beginning in block 121, analyzer 53 obtains data that characterizes the communication paths between each of access devices 51-1 through 51-N and hub 52. In at least some embodiments, this data includes the pre-equalizer tap coefficients from each of devices 51-1 through 51-N. As is known in the art, many communication systems employ pre-equalization to reduce or eliminate the effects of linear distortions caused by anomalies in a network. In the context of a pre-equalizer, each “tap” may correspond to a version of a received signal that can delayed by a predetermined amount and which is amplified (or attenuated) in accordance with a set of complex coefficients (known as tap coefficients). For example, a first tap may represent a version of the received signal with 0 delay that is modified in accordance with a first set of tap coefficients, a second tap may represent a version of the received signal having t delay that is modified in accordance with a second set of tap coefficients, etc. The outputs of the taps are typically summed to create a pre-equalized signal that is then transmitted across the network. In many cases, the tap coefficients can be adjusted on an adaptive basis so as to compensate for changes in network conditions. The number of taps, the temporal delay between taps, the manner of determining tap coefficients, and other parameters can vary among (and sometimes within) different equalization schemes.

In some embodiments, hub 52 includes a database storing the tap coefficients currently being used by each of access devices 51-1 through 51-N. Analyzer 53 obtains these tap coefficients using, e.g., one or more SNMP (simple network management protocol) queries directed to hub 52. In embodiments in which access network 50 is operated in accordance with a specification or standard, such as one or more Data-Over-Cable Service Interface Specification (DOCSIS) standards, for example, a CMTS or other termination system monitors communications from cable modems. Based on quality of the received signals, the termination system individually determines (and provides) the tap coefficients to be used by each modem for upstream communications. The termination system can thus maintain a record of the tap coefficients each modem is currently using. In other embodiments, analyzer 53 may obtain pre-equalization tap coefficients from a network element other than hub 52, and/or may obtain those coefficients directly from access devices.

FIG. 5A shows a portion of a database 150 generated by analyzer 53 and stored in memory 82 during the operations of block 121 in FIG. 4. For convenience, FIGS. 5A-5E show data in a simple table. The table of FIGS. 5A-5E is merely one example of how data can be arranged in accordance with some embodiments. The actual format of data and/or of the tables or other data structures used to organize that data will vary among different embodiments. Each row in table 150 corresponds to a specific one of access devices 51-1 through 51-N. The cells of each row contain data related to the corresponding access device and to the communication path used by the corresponding access device to communicate with hub 52. Cells in a first column 151 contain index numbers for table 150 rows. In the present example, row 00001 corresponds to device 51-1, row 00002 corresponds to device 51-2, etc. Fields in column 152 contain identifying data for an access device on a particular row. In some embodiments, this identifying data is a media access control (MAC) address of the access device. For each of columns 153-1 through 153-P, a cell on a particular row contains a set of tap coefficients for one of the pre-equalizer taps of the access device corresponding to that row. “P” represents an arbitrary number and will depend on the type of pre-equalization scheme being used. In some DOCSIS-compliant systems, for example, P equals 24. Each set of tap coefficients has a real (“r”) and imaginary (“i”) component, with those components represented generically as “<r>” and “<i>”. Although not shown in FIG. 5A, each of columns 153-1 through 153-P may include a row on each field that can hold a value to indicate whether a particular tap is the “main” tap (i.e., the tap corresponding to a zero time delay). At the end of step 121 (FIG. 4), each row of table 150 contains an identifier and up to P sets of tap coefficients for one of access devices 51-1 through 51-N.

Analyzer 53 then proceeds to block 122 and generates signature data for each of access devices 51-1 through 51-N. Further details of the operations of block 122 are shown in FIG. 6. During each of multiple loops through the subroutine of FIG. 6, analyzer 53 retrieves data for one of access devices 51-1 through 51-N, generates frequency response signatures for that access device, and approximates each signature using geometric shapes. Each of these operations is described more fully below. An incremental counter “i” controls iterations of the FIG. 6 loop. For convenience, the access device for which analyzer 53 is retrieving data, generating signatures, and approximating signatures during a particular loop iteration is called the i^(th) device.

In block 201, analyzer 53 sets counter i equal to a value corresponding to the first row index (00001) of table 150, thereby making the access device corresponding to that row the i^(th) device. Analyzer 53 then proceeds to block 202 and retrieves the tap coefficients for the i^(th) device from database 150. Analyzer 52 then proceeds to block 203 and normalizes those retrieved tap coefficients. As indicated above, the number of taps, the temporal delay between taps, the manner of determining tap coefficients, and other parameters can vary among (and sometimes within) different equalization schemes. All access devices in network 50 may not use the same pre-equalization scheme. Moreover, devices using the same scheme may implement that scheme in different ways. Although not shown in FIG. 5A, information regarding the pre-equalization scheme used by each access device and the manner of implementation can also be obtained as part of step 121 (FIG. 4). Using information regarding the pre-equalization scheme and scheme implementation for the i^(th) device, the tap coefficients for that device can be adjusted (or normalized) so as to be meaningful when compared to the normalized coefficients for other access devices in network 50. In some embodiments, normalization is used to accommodate different number, format and reporting schemes in a consistent manner. In one type of network, an example of tap coefficient normalization can be found in the document titled “DOCSIS® Best Practices and Guidelines Proactive Network Maintenance Using Preequalization CM-GL-PNMP-V01-100415” (Apr. 15, 2010) available from Cable Television Laboratories, Inc.

Analyzer 53 then continues to block 204 and performs a Fourier transform on the normalized i^(th) device tap coefficients. In some embodiments, analyzer 53 performs a Fast Fourier Transform (FFT) (e.g., a 100 point FFT), although other types of transforms can also be used. The Fourier transform of block 204 generates a frequency domain representation of the inverse of the amplitude/frequency response for a communication path the between the i^(th) device and hub 52. In some embodiments, analyzer 53 utilizes this inverse amplitude/frequency response as the amplitude/frequency response signature. In other embodiments, analyzer 53 generates an amplitude/frequency response signature for the i^(th) device in block 208 by inverting the inverse amplitude/frequency response.

An example of an amplitude/frequency response signature 300 is shown in FIG. 7A. The shape of signature 300 is chosen for purposes of explanation. The contours of a signature generated in block 208 in any given loop iteration will depend upon the coefficients obtained during that loop iteration. For purposes of explanation, FIG. 7A graphically shows signature 300 as a waveform similar to waveforms in FIG. 1A. In practice, however, analyzer 53 may not create a graphical rendering of a signature as part of the FIG. 6 subroutine or in connection with various other operations described herein. Instead, analyzer 53 may simply store a signature as an array of (x,y) coordinates for multiple points of the signature and perform various analyses by numerically manipulating those (x,y) coordinates. Of course, analyzer 53 may render signatures graphically in some embodiments and/or under certain circumstances. In some cases, for example, a network engineer may wish to see actual signatures so to look for various patterns indicative of specific types of plant anomalies.

After generating the amplitude/frequency response signature in block 208, analyzer 53 proceeds to block 209 and approximates that signature using simpler geometric shapes. FIG. 8 is a flowchart for a subroutine performing operations associated with block 209 of FIG. 6. In block 401, analyzer 53 traverses the array of graph points for a signature and identifies peaks and troughs of sufficiently large ripples in a signature. As seen in FIG. 1E, small ripples may be typical for communication paths in which there are no significant impairments. Relatively small y axis distances between adjacent peaks and troughs in such small ripples may indicate very minor amplitude fluctuations, and relatively small x axis distances between adjacent peaks and troughs may indicate amplitude fluctuations over a very narrow frequency range. In some circumstances, it may be useful to eliminate signatures that only have small ripples below certain thresholds. For example, a large portion of network 50 may be operating within normal parameters, and the network operator may be attempting to find problem areas.

As part of block 401, analyzer 53 identifies vector sign changes separated by minimum x axis and y axis threshold distances. In particular, a rising portion of a ripple represents increasing amplitude and a positive amplitude/frequency vector; a line tangent to a point on a rising portion of a ripple will have a positive slope. A falling portion of a ripple represents a decreasing amplitude and a negative amplitude/frequency vector; lines tangent to points on a falling ripple portion having negative slopes. A ripple peak represents a change from a positive amplitude/frequency vector to a negative amplitude/frequency vector. A ripple trough represents a change from a negative amplitude/frequency vector to a positive amplitude/frequency vector.

FIG. 7B illustrates identification of vector sign changes in block 401 according to some embodiments. Other techniques can be used. Analyzer 53 begins at x=0 and examines the y coordinate values of each successive point on signature 300 until it detects a vector sign change. In the present example, analyzer 53 detects the first vector sign change at point 301 of signature 300. Analyzer 53 then flags point 301 as a triangle vertex. As will become clearer below, analyzer 53 will ultimately approximate signature 300 with a series of adjacent triangles. Analyzer continues examining the y coordinate values of successive points on signature until the next vector sign change is found. In the current example, the next vector sign change occurs at point 302.

For each vector sign change found after the first vector sign change (all vector sign changes found after point 301 in the current example), analyzer 53 determines if that vector sign change is separated by a minimum x axis distance (Δx_(min)) and by a minimum y axis distance (Δy_(min)) from the previously flagged vertex (point 301 in the current example). Values for Δx_(min) and Δy_(min) can be established based on experience with a particular network and knowledge of typical problems that have historically occurred. In some networks, for example, amplitude/frequency responses having ripple magnitudes in excess of 5 dB may occur in 90% of cases that involve in-premises or tap-related problems. As another example, amplitude/frequency responses having eight or more ripples with magnitudes in less than 5 dB may occur in 75% of cases that involve reflection from an amplifier. As a further example, amplitude/frequency responses having ripple magnitudes in less than of 1 dB may be considered within normal operating parameters.

Because the x and y separation of points 301 and 302 exceed Δx_(min) and Δy_(min), respectively, point 302 is flagged as the next vertex. Analyzer 53 then continues and identifies the next vector sign change at point 303. Although the y distance between points 303 and the last vertex (point 302) exceeds Δy_(min), the x distance between points 303 and 302 is less than Δx_(min). Accordingly, analyzer 53 ignores point 303 and does not mark it as another vertex. Analyzer 53 then continues until it identifies the next vector sign change at point 304. Upon comparing point 304 to the last flagged vertex (point 302), analyzer 53 determines that the x axis separation between points 304 and 302 exceeds Δx_(min), but the y axis separation is less than Δy_(min). Accordingly, point 304 is also ignored. This process continues, and additional vertices 305, 306, 307 and 308 are identified.

As can be appreciated from the foregoing, the number of vertices identified for any particular signature will vary based on the specifics of that signature and on the values used for Δx_(min) and Δy_(min). Moreover, other techniques can be used to identify triangle vertices on a signature. In some instances, two different techniques may provide different results for the same signature. In general, however, this does not pose a problem. The ultimate purpose of identifying vertices is approximation of signatures so as to compare those signature approximations against each other. If the same technique is used to approximate all signatures in a set of signatures, any affect on vertex location resulting from differences in vertex identification techniques will impact the approximations of all signatures in that set in the same way.

After traversing all points of a signature in block 401 and identifying vertices, analyzer 53 continues to block 402. For some signatures, analyzer 53 may find not any vertices during the operations of block 1. For example, a signature may only include small ripples that have no peaks or valleys separated by both Δx_(min) and Δy_(min). Accordingly, analyzer 53 determines in block 402 if the operations of block 401 failed to identify vertices. If no vertices were identified, analyzer 53 proceeds on the “no” branch to block 403 and assigns an all-0 approximated signature value. The format of approximated signature values is discussed below. Analyzer 53 would then continue from block 403 to block 210 of FIG. 6. Block 210 of FIG. 6 is discussed below. If in block 402 analyzer 53 determines that vertices were identified in block 401, analyzer 53 continues to block 404 on the “yes” branch.

In block 404, analyzer 53 divides the signature into adjacent triangles using the vertices identified in block 401. This is illustrated in FIG. 7C. To avoid confusion, signature 300 is shown in broken line in FIG. 7C and the grid lines of the graph are omitted. Because a signature results from a Fourier transform and is thus circular, the far left side of the signature is a continuation of the far right side, and vice versa. Accordingly, at least one of the triangles will span the edges of the graph used to show signature 300. For example, triangle 1 (formed by vertices 301, 307 and 308) has a first portion at the far left of FIG. 7C and a second portion at the forth right of FIG. 7C. Triangle 2 (formed by vertices 301, 302 and 308) also has portions on the left and right sides of the graph. The remaining four triangles, which do not span the graph edges, are triangles 3 (vertices 305, 302 and 302), 4 (vertices 305, 306 and 302), 5 (vertices 307, 306 and 305) and 6 (vertices 307, 308 and 306).

Analyzer 53 then continues to block 405 and calculates areas for each of the triangles from block 404. This is illustrated in FIG. 7D, which shows triangles 1-6 removed from the graph of FIGS. 7A-7C. For convenience the area of triangle 1 is shown as “A1,” the area or triangle 2 shown as “A2,” etc. After calculating triangle areas, analyzer 53 continues to block 406 and generates an approximated signature value for the signature based on the number of triangles and the triangle areas. In some embodiments, the approximated signature value has a multibyte format in which the first byte specifies the number of triangles, and in which each successive byte contains the area for one of the triangles. Accordingly, the approximated signature value for signature 300 according to the current example would be as shown in FIG. 7E. Triangle area byte value fields could be populated according to any desired convention. For example, and as shown in FIG. 7E, some embodiments populate the first area value byte field with the area of the triangle having a portion at the bottom of the far left. Subsequent fields are then populated by traversing adjacent triangles across shared sides until all triangle areas have been added to the signature approximation. Although the example approximated signature of FIG. 7E is seven bytes in length in the present example, the byte length for signature approximations will vary based on the number vertices (and thus the number of triangles) found when approximating a signature. From block 406 of FIG. 8, analyzer 53 proceeds to block 210 of FIG. 6. In block 210, and as shown in FIG. 5B, analyzer 53 stores the amplitude/frequency response signature approximation for the i^(th) device in database 150. The values “A1,” “A2,” etc. in FIGS. 5E and 7E are only meant to generically represent the values of triangle areas and are not necessarily intended as hexadecimal representations of actual areas.

Analyzer 53 then continues to block 211 and generates a group delay/frequency response signature for the i^(th) device using the Fourier transform previously performed for the i^(th) device at block 204. Generation of a group delay/frequency response signature from a frequency domain representation of a channel response (or of an inverse channel response) is a technique known to persons of ordinary skill and thus not described herein. As with the amplitude/frequency response signature discussed above, analyzer 53 may use an inverse group delay/frequency response as the group delay/frequency response signature, or may generate a group delay/frequency response signature by inverting an inverse group delay/frequency response.

As explained above in connection with FIGS. 1A-1I, the ripples in a group delay/frequency response signature may differ from those of an amplitude/frequency response signature. Thus, analyzer 53 continues to block 212 and repeats the approximation operations previously performed in block 209, but instead using the group delay/frequency response signature generated for the i^(th) device in block 211. When performing the approximation in block 212, however, analyzer 53 may utilize values for Δx_(min) and/or Δy_(min) that are different from the values used when performing approximation operations in block 209. The output of block 212 is a group delay/frequency response signature approximation that has the same format as that shown in FIG. 7E. However, a group delay/frequency response signature approximation for the i^(th) device may based on more or fewer triangles than were utilized in creating the amplitude/frequency response signature approximation for the i^(th) device, and those triangles may have different areas. The output of block 212 could also be an all-0 value if the group delay/frequency response signature had ripples below the applicable Δx_(min) and/or Δy_(min) values. In block 216, and as shown in FIG. 5C, the i^(th) device group delay/frequency response signature approximation is stored in database 150 (shown generically as “<gd/f resp. sig. approx.”).

Analyzer 53 then continues to block 217 and generates a phase delay/frequency response signature for the i^(th) device using the Fourier transform previously performed for the i^(th) device at block 204. Generation of a phase delay/frequency response signature from a frequency domain representation of a channel response (or of an inverse channel response) is also a common technique known to persons of ordinary skill. As with the amplitude/frequency response signature discussed above, analyzer 53 may use an inverse phase delay/frequency response as the phase delay/frequency response signature, or may generate a phase delay/frequency response signature by inverting an inverse phase delay/frequency response.

Because a phase delay/frequency response signature may also be different from the signatures generated in blocks 208 and 211, analyzer 53 continues to block 218 and repeats the approximation operations previously performed in blocks 209 and 212, but now using the phase delay/frequency response signature generated for the i^(th) device in block 217. Analyzer 53 may utilize values for Δx_(min) and/or Δy_(min) that are different from the values used when performing approximation operations in block 209 or in block 212. The output of block 218 is a phase delay/frequency response signature approximation that has the same format as that shown in FIG. 7E, but which may have data based on a different number of triangles (and/or triangles of different shapes) than were used in blocks 209 or 212. The output of block 218 could also be an all-0 value if the phase delay/frequency response signature had ripples below the applicable Δx_(min) and/or Δy_(min) values. In block 219, and as shown in FIG. 5D, the i^(th) device phase delay/frequency response signature approximation is stored in database 150 (shown generically as “<pd/f resp. sig. approx.”).

Analyzer then continues from block 219 to block 220 and determines if there are additional devices in database 150 for which the operations of blocks 201 through 219 should be performed. If so (i.e., if i<N), analyzer 53 proceeds on the “no” branch to block 221 and increments counter i. Analyzer 53 then returns from block 221 to block 202 and repeats the operations of block 202 through block 219 for the next access device. If in block 220 analyzer 53 determines that there are no more access devices for which the operations of block 202 through block 219 should be performed, analyzer proceeds on the “yes” branch from block 220 to block 123 of FIG. 4.

In block 123, analyzer 53 then utilizes the signature approximations to sort signatures into clusters based on similarities between signatures. Specifically, analyzer 53 first sorts all of the amplitude/frequency response signature approximations, then sorts all of the group delay/frequency response signature approximations, and then sorts all of the phase delay/frequency response signature approximations. As a result of this sorting, various clusters of signatures similar to those indicated in FIGS. 1B-1M can be identified.

Various methods can be used to compare signature approximations when performing sorting operations. In some embodiments, only the first byte (number of triangles) is used. Thus, one cluster might identify signatures for which approximations had no triangles, another cluster might identify signatures for which approximations had two triangles, etc. In still other embodiments, both the number of triangles and the sizes of triangles are compared. For example, two signature approximations might be sorted into the same cluster if each has the same value in the first byte (i.e., same number of triangles) and if area bytes for a similar triangle position are within a designated percentage of one another (e.g., if the second byte value in one of those signature approximations is within 10% of the second byte value in the other of those signature approximations, etc.). Still other sorting methods can be used.

At the conclusion of block 123, signatures of each type are assigned to different clusters. As shown in FIG. 5E by columns 157-159, these cluster assignments can be stored in fields of database 150 as numbers or other identifiers used to identify various clusters. For example, all devices associated with a cluster of amplitude/frequency response signatures would have a specific value identifying that cluster in a field of column 157 on the row corresponding to that device.

In block 124, analyzer 53 selects one or more clusters that may be of interest. In some cases, a user of analyzer 53 provides (or may have previously provided) input that identifies a specific access device. Based on identification of that specific access device, analyzer 53 may then identify all other access devices that are associated with a signature in the same cluster as a signature for the identified devices. A network operator may identify a specific access device for any of various reasons, one example of which is further discussed below. As another example, a user of analyzer 53 may provide (or may have previously provided) input requesting identification of signatures having certain specific characteristics. Based on the specified characteristics, analyzer 53 may then identify signatures having those characteristics and identify access devices associated with those signatures. An example of signature identification in this manner is also described below.

In block 125, analyzer 53 obtains geospatial location data for each access device in the selected cluster(s) from block 124. In some embodiments, analyzer 53 may obtain this data from a separate database that maintains information about each access device authorized to operate in network 50. This separate database could be, e.g., an account database having addresses for premises at which authorized access devices are deployed.

In block 126, analyzer 53 outputs information to a user regarding locations of access devices in the cluster(s) of interest. In some embodiments, and as shown in FIG. 9A, analyzer 53 outputs this information on display 86 (FIG. 2) in the form of a map showing access device locations. In the example of FIG. 9A, devices in the cluster of interest are identified with highlighted icons 501-509. Devices not in the cluster of interest can be shown with unhighlighted icons (black rectangles in FIG. 9A). In some embodiments, additional information regarding devices in the cluster of interest can be displayed automatically or in response to additional user input (e.g., such as hovering a cursor over one of icons 501-509). Such information could include MAC address for a device, a device IP address, the name of a customer or other person associated with a device in a billing or other database, current performance data for a device, etc.

In many large networks, persons sometimes obtain service without permission from the network operator. For example, an unscrupulous person may move into a house, apartment, office or other premises that is within the service area of network 50. That premises may already be equipped with a physical connection to network 50 (e.g., in connection with a previous occupant). However, the unscrupulous person may not have entered into an agreement with the network 50 operator to pay for service and/or to otherwise abide by appropriate network usage policies. If the unscrupulous person obtains an access device and copies provisioning information from an authorized access device, the unscrupulous person might then be able to connect his unauthorized device to network 50 and obtain service. Conventional techniques for identifying such unauthorized devices can be labor intensive and may interfere with service provided to authorized devices. In some embodiments, analyzer 53 can utilize signature data to locate access devices that are using network 50 without authorization.

FIG. 10 is a block diagram showing operations of analyzer 50, according to at least some embodiments, when locating unauthorized devices. In at least some embodiments, the operations of blocks 601 and 602 are performed as part of the operations of block 124 of FIG. 4. In block 601, analyzer 53 receives an identification of an unauthorized device in network 50. This identification could be, e.g., a user input specifying a particular MAC address or other identifier. The operator of network 50 may become aware of unauthorized devices in any of various manners. In some embodiments, for example, analyzer 53 or another network element may periodically comb device identifiers in database 150 for unauthorized devices. Unauthorized devices can be identified in any of various ways. As one example, the MAC address of each device in table 150 can be compared against other databases having information about authorized devices. If a particular MAC address in table 50 cannot be found in one of those other databases, that MAC address likely represents an unauthorized device. As another example, an unscrupulous person may have copied a MAC address from the same authorized device from which the unscrupulous person obtained provisioning information for his unauthorized device. Accordingly, a determination can be made as to whether two devices in table 150 (or two devices in a larger network of which access network 50 is a part) are using the same MAC.

In response to identification of an unauthorized device, and as shown in block 602, analyzer 53 determines clusters for the response signatures of the unauthorized device. For example, analyzer 53 may check the cluster identifier in the field of column 157 of table 150 (see FIG. 5E) on the row corresponding to the unauthorized device. Using the cluster identifier in that field, analyzer 53 then identifies other devices having amplitude/frequency response signatures in the same cluster. Analyzer 53 may then repeat these steps for the cluster identifier in column 158 so as to identify other devices having group delay/frequency response signatures in the same cluster as the unauthorized device, and for the cluster identifier in column 159 so as to identify other devices having phase delay/frequency response signatures in the same cluster as the unauthorized device.

Analyzer 53 then continues from block 602 to block 125 (FIG. 4) and obtains geospatial location data for authorized devices in the one or more clusters identified in block 602. Analyzer 53 then proceeds to block 126 of FIG. 4 and outputs a display of locations for such authorized devices. An example of such a display is shown in FIG. 9B. Because the unauthorized device may not be listed in the billing or other databases of the network 50 operator, the analyzer 53 may not have geospatial location for the unauthorized device. However, analyzer 53 will likely have geospatial location data for other devices associated with signatures similar to a signature associated with the unauthorized device. In other words, analyzer 53 will likely have location information for authorized devices associated with signatures in a cluster that also includes a signature associated with the unauthorized device. Based on the locations of those authorized devices, the network operator knows that the unauthorized device is likely in the same area. In some embodiments, and as shown in FIG. 9B, analyzer 53 provides a display showing an area (box 515) in which an unauthorized device is likely located and one or more corresponding dialog displays 516. In some embodiments, analyzer 53 might only highlight the authorized devices (511-514 in the present example) associated with a signature cluster also associated with the unauthorized device.

If available, plant mapping data (e.g., locations of taps, feeder lines and/or other elements) can be used to estimate an area such as box 515 or to otherwise identify possible locations of the unauthorized device. If devices 511-514 all share the same tap, for example, the unauthorized device is likely located at a premises that is also connected to network 50 through that same tap. If devices 511-514 do not share a common tap but instead share some component further upstream (e.g., if they are served by different feeders from a common trunk), the unauthorized device is likely located at a premises that is also connected to network 50 via that common element. Alternatively (or in addition), an area such as box 515 can be estimated using an adjustable radius or other distance from authorized devices associated with a signature cluster also associated with the unauthorized device.

Once the network 50 operator has narrowed the geospatial region in which an unauthorized device is located, the operator can take additional steps to find the unauthorized device. For example, the operator could consult other databases or records and determine what premises in that region have be physically connected to network 50. The operator could then determine which of those connected premises should be active (e.g., which premises are covered by an appropriate agreement with an end user) and which should be inactive. The operator could then disconnect network connections at premises that should be inactive.

As indicated above, a device may be associated with one cluster of amplitude/frequency response signatures, with a different cluster of group delay/frequency response signatures, and with yet another cluster of phase delay/frequency response signatures. Each of those clusters may have different associated devices, and one (or two) of the clusters may have a much larger number of associated devices that the third cluster. In some embodiments, analyzer 53 may allow user input to selectively cause display of devices co-associated with the unauthorized device in a cluster for each type of signature. For example, a display of authorized devices co-associated with the unauthorized device's amplitude/frequency response signature may result in a small number of devices in a relatively concentrated area. However, the unauthorized device may have a normal group delay/frequency response signature in a cluster that is associated with a larger number of devices over a larger area. In some embodiments, analyzer 53 can be configured to automatically select the unauthorized device signature cluster having the fewest associated authorized devices and to display those authorized devices in that automatically selected cluster.

In some cases, an unauthorized device may not have a signature that is sufficiently unique to narrow the device location to particular region. For example, each of the amplitude/frequency, group delay/frequency and phase delay/frequency response signature may be part of a large cluster (e.g., a “normal” or “rope” cluster) having numerous signatures. This could occur, e.g., if the unauthorized device is located in an area where no plant anomalies are causing significant distortions. In some embodiments, this can be addressed by repeating operations of blocks 121-123 for all devices associated with a signature in one of those large clusters. When repeating those operations, however, the Δx_(min) and/or Δy_(min) values used during signature approximation (described, e.g., in connection with block 801 of FIG. 8) can be reduced so as to better discriminate among signatures.

In some embodiments, differences between different types of signatures for a specific device can also be used to locate certain types of plant anomalies. As but one illustration, signature differences can be used to locate faulty or missing end-of-line (EOL) terminators in an access network, such as an HFC access network. Many networks employ EOL terminators to reduce microreflections in the coaxial portion of the plant. As is known in the art, an EOL terminator is a physical connector having a 75Ω resistor installed on unused cable connection positions on a line tap to avoid impedance mismatch. If an EOL terminator is missing or damaged, resulting microreflections can cause signal distortion. Conventional techniques for identifying damaged or missing EOL terminators are labor intensive, time-consuming and expensive. In particular, skilled technicians are periodically dispatched to physically examine and test EOL terminators on each tap in large portions of a network. In many cases, such taps are located on telephone poles, and accessing such taps requires the use of a bucket lift truck or other specialized equipment.

FIGS. 11A-11C are examples of frequency response signatures consistent with faulty or missing end-of-line terminators affecting a portion of devices in a network. In many cases, a faulty or missing EOL terminator will cause significant amplitude distortion. For example, FIG. 11A shows amplitude/frequency response signatures for 158 devices. A small cluster of those signatures has a large ripple indicative of amplitude distortion. Frequently, however, a faulty of missing EOL terminator will cause little of no group delay or phase delay. FIG. 11B shows group delay/frequency response signatures for the same devices associated with signatures of FIG. 11A, and generally represents no significant group delays for any of those devices. FIG. 11C shows phase delay/frequency response signatures for the same devices associated with signatures of FIG. 11A, and generally represents no significant phase delays for any of those devices. Moreover, many networks utilize taps that have directional isolation. If a cable connection position on such a tap has a faulty or missing EOL connector, any resulting distortion is limited to devices sharing that tap.

In some embodiments, analyzer 53 locates taps having faulty or missing EOL terminators by identifying devices having an amplitude/frequency response signature meeting certain characteristics indicative of amplitude distortion and also having group delay/frequency response and phase delay/frequency response signatures indicative of no significant group or phase delay. Once such devices are found, they can be located using associated geospatial data. Knowledge of tap locations in the network physical plant can then be used to determine which tap(s) likely have faulty or defective EOL terminators.

FIG. 12 is a flow chart showing operations performed by analyzer 53 when attempting to localize faulty or missing EOL terminators. In some embodiments, the operations of blocks 701-703 are performed as part of the operations of block 124 of FIG. 4. In block 701, in response to a received instruction, analyzer 53 begins identifying devices in database that may be communicating through a tap having a faulty or missing EOL terminator. In block 702, analyzer 53 identifies devices in database 150 associated with an amplitude/frequency response signature meeting a first set of criteria consistent with faulty or missing end-of-line terminators. For example, a set of criteria for finding problems in a single tap located at the end of a line could specify that a signature should have two detectable ripples with a peak/valley threshold of 4 dB, and that there should be at least one and no more than eight common signatures present. Analyzer 53 then proceeds to block 703 and identifies devices, from within the devices identified in block 702, associated with a group delay/frequency response signature meeting a second set of criteria and associated with a phase delay/frequency response signature meeting a third set of criteria. In at least some embodiments, the second set of criteria could specify that the group delay/frequency response signature has no ripples exceeding a certain magnitude. The third set of criteria could similarly specify that the phase delay/frequency response signature has no ripples exceeding a certain magnitude.

After identifying devices associated with signatures meeting the specified criteria in blocks 702 and 703, analyzer 53 proceeds to block 125 (FIG. 4) and obtains geospatial location data for the devices identified in block 703. Analyzer 53 then proceeds to block 126 of FIG. 4 and outputs a display of locations for such devices. An example of such a display is shown in FIG. 9C, where analyzer 53 has highlighted devices 520-525 at the end of Street A. Using knowledge of locations within network 50, the network 50 operator can then determine which taps in network 50 serving the devices indicated in the display of FIG. 9C. Although FIG. 9C shows one set of indicated devices for convenience, this need not be the case. In some cases, for example, analyzer 53 might identify a first set of devices in a first region, a second set of devices in a second region, etc. In some embodiments, tap locations may also maintained in a database accessible by analyzer 53. In such embodiments, locations of taps serving devices associated with signatures meeting the first, second and third sets of criteria could be displayed.

In some embodiments, the identification of devices during the operations of FIG. 12 can be checked by evaluating (or re-evaluating) signatures associated with devices served by a tap directly upstream from a tap serving the identified devices. If those devices served by the upstream tap are not associated with signatures meeting the first, second and third sets of criteria, the faulty or missing EOL terminator is likely located on the downstream tap or at some location downstream from the downstream tap.

Numerous variations on the methods and systems described above can be employed in various other embodiments. As but one example, certain operations described in connection with various flow charts can be rearranged, omitted or replaced with other operations. Various aspects of the algorithms described in connection with various operations can also be varied. For example, signatures can be approximated in numerous different ways. In some embodiments, for example, a signature approximation is calculated in block 406 of FIG. 8 (and in similar operations in connection with blocks 212 and 218 of FIG. 6) by summing the triangle areas, thereby yielding a signature approximation quantifiable with a single number. Signature approximations calculated in such a manner can be easily compared (e.g., signatures are included in a cluster if their area summations are within a predetermined percentage of a predetermined value). In other embodiments, features of triangles other than area are used when approximating a signature. For example, each triangle found in block 404 of FIG. 8 (and in similar operations in connection with blocks 212 and 218 of FIG. 6) can be characterized based on the length of a longest side and the measure of one or more angles in the triangle, based on triangle perimeter length, etc. Indeed, geometric shapes other than triangles can be used when approximating signatures.

Although the above embodiments were described in the context of a system that employs adaptive pre-equalization, other embodiments can readily perform similar methods in networks that employ adaptive post-equalization. As indicated above, embodiments are not limited to HFC networks. For example, numerous other network types employ some form of quadrature amplitude modulation and/or phase shift keying modulation, and also employ some form of adaptive equalization. Methods, systems and devices described above can readily be adapted to such networks.

In some embodiments, techniques such as are described herein can be combined with analysis of channel characteristics after equalization (or pre-equalization) has been performed. For example, analyzer 53 could be further configured to generate amplitude/frequency response, group delay/frequency response and phase delay/frequency response signatures based on the upstream communications from devices as received at hub 52. This would, in effect, indicate the effectiveness of pre-equalization performed at the access devices prior to upstream transmission. This information could be used, e.g., to identify non-linear distortions that cannot be canceled by equalization.

Embodiments also include one or more tangible machine-readable storage media (e.g., a CD-ROM, CD-RW, DVD, floppy disc, FLASH memory, RAM, ROM, magnetic platters of a hard drive, etc.) that store instructions executable by one or more processors to carry out one or more of the operations described herein. As used herein (including the claims), a tangible machine-readable storage medium is a physical structure that can be touched by a human. A signal would not by itself constitute a tangible machine-readable storage medium, although other embodiments may include signals or other ephemeral versions of instructions executable by one or more processors to carry out one or more of the operations described herein.

The foregoing description of embodiments has been presented for purposes of illustration and description. The foregoing description is not intended to be exhaustive or to limit embodiments to the precise form disclosed, and modifications and variations are possible in light of the above teachings or may be acquired from practice of various embodiments. The embodiments discussed herein were chosen and described in order to explain the principles and the nature of various embodiments and their practical application to enable one skilled in the art to utilize the present invention in various embodiments and with various modifications as are suited to the particular use contemplated. All embodiments need not necessarily achieve all objects or advantages identified above. Any and all permutations of various features described herein are within the scope of the invention. 

1. A method comprising: generating, using one or more processors and for each of multiple access devices in communication with a hub device in a network, at least one associated frequency response signature based on communications between that access device and the hub device; calculating a signature approximation for each of the frequency response signatures; associating each frequency response signature with one of multiple signature clusters, wherein each frequency response signature is associated with one of the clusters based on similarities between the signature approximation of the frequency response signature and signature approximations of other frequency response signatures associated with that cluster; and identifying at least one of the access devices based on identification of one of the signature clusters associated with the at least one access device.
 2. The method of claim 1, wherein the network comprises a hybrid fiber coaxial network.
 3. The method of claim 1, wherein the generating comprises, for each of the multiple access devices, performing a Fourier transform using adaptive equalization coefficients specific to communications between that access device and the hub device, and wherein for each frequency response signature the signature approximation is derived from geometric shapes mapped to portions of the response signature.
 4. The method of claim 1, wherein the calculating comprises, for each of the frequency response signatures, deriving a signature approximation from triangles mapped to portions of the frequency response signature.
 5. The method of claim 4, wherein each of the signature approximations includes a first value representing a number of mapped triangles used to derive the signature approximation and a plurality of additional values representing areas of those mapped triangles.
 6. The method of claim 4, wherein each of the signature approximations includes a value representing a sum of areas of mapped triangles used to derive the signature approximation.
 7. The method of claim 1, wherein the identifying comprises identifying one or more authorized access devices having known locations based on identification of a signature cluster associated with an unauthorized access device having an unknown location.
 8. The method of claim 1, wherein the at least one associated frequency response signature comprises, for each of the multiple access devices, an amplitude/frequency response signature, a group delay/frequency response signature and a phase delay/frequency response signature.
 9. The method of claim 8, wherein the identifying comprises identifying access devices associated with an amplitude/frequency response signature having a first set of criteria, associated with a group delay/frequency response signature having a second set of criteria different from the first set of criteria, and associated with a phase delay/frequency response signature having a third set of criteria different from the first set of criteria.
 10. A tangible machine-readable storage medium storing machine-executable instructions for performing a method comprising: generating, using one or more processors and for each of multiple access devices in communication with a hub device in a network, at least one associated frequency response signature based on communications between that access device and the hub device; calculating a signature approximation for each of the frequency response signatures; associating each frequency response signature with one of multiple signature clusters, wherein each frequency response signature is associated with one of the clusters based on similarities between the signature approximation of the frequency response signature and signature approximations of other frequency response signatures associated with that cluster; and identifying at least one of the access devices based on identification of one of the signature clusters associated with the at least one access device.
 11. The tangible machine-readable storage medium of claim 10, wherein the network comprises a hybrid fiber coaxial network.
 12. The tangible machine-readable storage medium of claim 10, wherein the generating comprises, for each of the multiple access devices, performing a Fourier transform using adaptive equalization coefficients specific to communications between that access device and the hub device, and wherein for each frequency response signature the signature approximation is derived from geometric shapes mapped to portions of the response signature.
 13. The tangible machine-readable storage medium of claim 10, wherein the calculating comprises, for each of the frequency response signatures, deriving a signature approximation from triangles mapped to portions of the frequency response signature.
 14. The tangible machine-readable storage medium of claim 13, wherein each of the signature approximations includes a first value representing a number of mapped triangles used to derive the signature approximation and a plurality of additional values representing areas of those mapped triangles.
 15. The tangible machine-readable storage medium of claim 13, wherein each of the signature approximations includes a value representing a sum of areas of mapped triangles used to derive the signature approximation.
 16. The tangible machine-readable storage medium of claim 10, wherein the identifying comprises identifying one or more authorized access devices having known locations based on identification of a signature cluster associated with an unauthorized access device having an unknown location.
 17. The tangible machine-readable storage medium of claim 10, wherein the at least one associated frequency response signature comprises, for each of the multiple access devices, an amplitude/frequency response signature, a group delay/frequency response signature and a phase delay/frequency response signature.
 18. The tangible machine-readable storage medium of claim 17, wherein the identifying comprises identifying access devices associated with an amplitude/frequency response signature having a first set of criteria, associated with a group delay/frequency response signature having a second set of criteria different from the first set of criteria, and associated with a phase delay/frequency response signature having a third set of criteria different from the first set of criteria.
 19. An apparatus comprising: at least one processor; and at least one memory having stored therein machine executable instructions, the at least one memory and the instructions stored thereon configured, with the at least one processor, to cause the apparatus to generate, for each of multiple access devices in communication with a hub device in a network, at least one associated frequency response signature based on communications between that access device and the hub device, calculate a signature approximation for each of the frequency response signatures, associate each frequency response signature with one of multiple signature clusters, wherein each frequency response signature is associated with one of the clusters based on similarities between the signature approximation of the frequency response signature and signature approximations of other frequency response signatures associated with that cluster, and identify at least one of the access devices based on identification of one of the signature clusters associated with the at least one access device.
 20. The apparatus of claim 19, wherein the apparatus is part of a system that includes the multiple access devices and the hub device. 